1.7.3. Workflow Settings
The User-Defined Workflows
option allows you to specify whether you want users to be able to deploy
declarative workflows, such as those that are created using Microsoft
SharePoint Designer 2010, on sites in this Web application. The default setting enables deployment of declarative workflows.
The Workflow
Task Notifications specifies whether you allow either or both of the
following kinds of nonauthenticated users to participate in workflows.
Internal users receive an e-mail message that explains how to request access to the site (subject to administrator approval). External users receive an e-mail message that contains the attached document or list item for them to review or sign.
1.7.4. Outgoing E-mail
All messages sent from SharePoint 2010, such as alerts, notifications, and site invitations, require an SMTP
server to route the messages. This SMTP server can be any
SMTP-compliant server, but you must be able to connect to it using port
25 from your SharePoint 2010 server. For example, you can use either the
IP address, NetBIOS name, or the fully qualified domain name of your
SMTP server, as long as all services necessary to locate the server are
in place.
Note:
Firewalls between the Office
SharePoint Server 2007 server and the mail server can cause outgoing
mail to fail, so make sure that SMTP traffic is allowed.
When configuring your Web application’s outgoing e-mail server settings,
you can specify a different Outbound SMTP Server, From address, and
Reply-to address for a specific Web application. For example, you could
have e-mail sent to recipients from the address [email protected] but then specify [email protected] as the reply address for the e-mail. The outgoing e-mail settings at this level override the settings configured at the farm level.
1.7.5. Mobile Account
A new feature in SharePoint 2010 allows administrators to configure a corporate Short
Message Service (SMS) that can deliver alerts and notifications to
users. This lets administrators receive system notification or health
and monitoring alerts directly to their Windows mobile devices. You can
also use a third-party SMS, and there is the option to specify a user name and password if required when the service is accessing the SMS provider.
1.7.6. SharePoint Designer
These are the same SharePoint Designer settings found under General Application
Settings in Central Administration. They are used to specify whether
SharePoint Designer is available for use within a Web
application and if so what tasks can be performed using SharePoint
Designer. There are four settings you can configure, as explained in the
following list.
Allow SharePoint Designer To Be Used In This Web Application Use this setting to specify whether users can edit sites using SharePoint Designer.
Allow Site Collection Administrators To Detach Pages From The SiteTemplate
Use this setting to specify whether to allow site administrators to
detach pages from the original site definition using SharePoint
Designer. Site collection administrators are always able to perform this
operation.
Allow Site Collection Administrators To Customize Master Pages And Layout Pages
Use this setting to specify whether to allow site administrators to
customize master pages and layout pages using SharePoint Designer. Site
collection administrators are always able to perform this operation.
Allow Site Collection Administrators To See The URL Structure Of Their Web Site
Use this setting to specify whether to allow site administrators the
ability to view and manage the URL structure of their website using
SharePoint Designer. Site collection administrators are always able to
perform this operation.
1.7.7. Manage Features
There are also features that
can be managed at the Web application level. This option allows you to
activate or deactivate any of the default Web application features or
any Web application custom features that have been installed. Similar to
the farm level features, these features can be managed through Central
Administration or from the command line using Windows PowerShell or
STSADM.
1.7.8. Managed Paths
Managed paths indicate which parts of the URL namespace is managed by each Web application
in IIS. It also provides a way to define a taxonomy within the
namespace by creating new site collections and associating them with
specific namespaces, such as projects, as shown in Figure 8.
There are two types of managed paths, explicit and wildcard. You use an
explicit managed path to allow only a single site collection with a
specific namespace, such as /ProjectA. You use a wildcard to create a
category of site collections that includes the namespace in the URL and
then all site collection names after it, such as /Projects/ProjectA.